Printing system and methods to manage printing devices according to information for each printing device

ABSTRACT

A printing system manages printing devices. A managing server receives device update status information and pending job information from each of the printing devices. A status change for a component within a first printing device is detected, thereby updating the device information for the first printing device. The managing server parses a print job queue for the first printing device to update the pending job information to determine the print job will cause a first potential error related to the changed status of the first printing device. When a new print job is received, the managing server determines that the new print job will not occur according to the first potential error, identifies a second printing device, determines the new print job will not result in a second potential error at the second printing device, and sends the new print job to the second printing device.

FIELD OF THE INVENTION

The present invention relates to a system of printing devices thatimplements methods to manage print jobs to the printing devices usinginformation specific to each printing device, such as error informationand pending job information.

DESCRIPTION OF THE RELATED ART

When an error, such as an empty paper tray, occurs on a printing device,print operations are suspended for that device if it us feeding fromthat tray. Some systems may notify the error to the user so that theuser can act on the error to resolve it. This reaction-type processcreates additional down-time for the printing device. It also createsmore wasted time for the user, especially in a print-heavy environmentsuch as production printing, because the user reacts to the media-causederror created by the current print job. The user does not have theinformation or notification that future print jobs may cause similar oradditional errors while addressing the current one.

SUMMARY OF THE INVENTION

A method for managing a plurality of printing devices within a printingsystem is disclosed. The method includes receiving device informationfor each of the plurality of printing devices, in which the deviceinformation includes status of components within each of the printingdevices, subscribing to receive device update status information andpending job information from each of the plurality of printing devices,in which the device update status information and pending jobinformation is stored with the device information for each of theplurality of printing devices, detecting a status change for one of thecomponents within a first printing device of the plurality of printingdevices, updating the device information for the first printing device,and parsing a print job queue for the first printing device to updatethe pending job information, in which at least one print job is in theprint job queue will change a status of the first printing device. Themethod further includes determining the at least one print job willcause a first potential error related to the changed status of the firstprinting device, receiving a new print job for the printing system,determining that the new print job will not occur according to the firstpotential error at the first printing device based on the deviceinformation, device update status information, or pending jobinformation of the first printing device, identifying a second printingdevice of the plurality of printing devices, determining the new printjob will not result in a second potential error at the second printingdevice based on its device information, device update statusinformation, and pending job information of the second printing device;and sending the new print job to the second printing device.

A method of managing print jobs using a plurality of printing devices isalso disclosed. The method includes obtaining from each printing deviceof the plurality of printing devices at least the following information:job information about one or more print jobs pending at the printingdevice, error information about one or more errors on the printingdevice, warning information about one or more warnings on the printingdevice, and function information about one or more functions availableat the printing device. Based on the obtained information, the methoddetermines an error priority order of the plurality of printing devicesbased on the error information and the warning information, receives aprint job of a document, wherein the print job specifies resourcesneeded to complete printing of the document, determines that theresources for the print job will cause an error condition at one or moreprinting devices of the plurality of printing devices using the jobinformation, updates the error priority order based on the errorcondition at the one or more printing devices, determines a printingdevice from the plurality of printing devices to receive the print jobof the document according to the function information of each printingdevice and the error priority order, wherein the printing deviceprocesses the print job without causing the error condition, sends theprint job to the printing device, and updates the job information forthe printing device.

Further, a method for processing a print job for a document isdisclosed. The method comprising querying a first printing device of aplurality of printing devices for first job information about at leastone pending print job in a first print queue, first error informationabout at least one error on the first printing device, and firstfunction information about at least one function available at the firstprinting device, and querying a second printing device of the pluralityof printing devices for second job information about at least onepending print job in a second print queue, second error informationabout at least one error on the second printing device, and secondfunction information about at least one function available at the secondprinting device. The method further includes analyzing the first errorinformation and the second error information to prioritize the at leastone error on each of the first and second printing devices, determiningan error priority order between the first and second printing devices,receiving the print job of a document, wherein the print job specifiesresources to complete printing of the document, determining whether theresources specified by the print job will cause a first potential errorcondition on the first printing device based on the first jobinformation, determining whether the resources of the print job willcause a second potential error condition of the second printing devicebased on the second job information, updating the error priority orderbased on the first potential error condition and the second potentialerror condition caused by the print job, and sending the print job toone of the first printing device and the second printing device based onthe error priority order and the function information for each printingdevice.

A method for resolving errors within a printing system is furtherdisclosed. The method includes compiling error information about errorsfrom a plurality of printing devices, compiling pending job informationfor pending print jobs at the plurality of printing devices, analyzingthe error information about the errors from the plurality of printingdevices, determining an error category for each of the errors based onthe error information, applying weight parameters to each of the errorsaccording to the respective error category, analyzing the pending jobinformation for the pending print jobs at the plurality of printingdevices to determine resources specified by each pending print job,indicating that the resources specified by each pending print job willresult in a potential error at a printing device of the plurality ofprinting devices, applying the weight parameters to the potential error,and determining a priority order to resolve the errors and the potentialerror based on the weight parameters and the pending job information forthe pending print jobs.

A further method for resolving errors at a printing device is alsodisclosed. The method includes compiling error information about aplurality of errors, compiling pending job information for pending printjobs at a print queue, analyzing the error information about theplurality of errors, determining an error category for each of theerrors based on the error information, applying weight parameters toeach of the errors according to the respective priority category,analyzing the pending job information for the pending print jobs todetermine resources specified by each pending print job, indicating thatthe resources specified by each pending print job will result in apotential error within the printing device, applying the weightparameters to the potential error, and determining a priority order toresolve the errors and the potential error based on the weightparameters.

A print managing server for a printing system is also disclosed. Theprint management server includes a processor and a memory to storeinstructions executable on the processor. According to the embodiment,the instructions, when executed, configure the server to compile errorinformation about errors from a plurality of printing devices, compilepending job information for pending print jobs at the plurality ofprinting devices, analyze the error information about the errors fromthe plurality of printing devices, determine an error category for eachof the errors based on the error information, apply weight parameters toeach of the errors according to the respective priority category,analyze the job information for the pending print jobs at the pluralityof printing devices to determine resources for each pending print job,indicate that the resources for each pending print job will result in apotential error at the respective printing device, apply the weightparameters to the potential error, and determine a priority order toresolve the errors and the potential error based on the weightparameters and the job information for the pending print jobs.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other features and attendant advantages of the present inventionwill be more fully appreciated when considered in conjunction with theaccompanying drawings.

FIG. 1 illustrates a block diagram of a printing system of a pluralityof printing devices for controlling and monitoring printing performancesof the plurality of printing devices according to the disclosedembodiments.

FIG. 2 illustrates a block diagram of a printing system of a pluralityof printing devices using a managing server to control and monitoringprinting performances of the plurality of printing devices according tothe disclosed embodiments.

FIG. 3 illustrates a block diagram of components of a printing deviceaccording to the disclosed embodiments.

FIG. 4 illustrates a block diagram of a managing server according to thedisclosed embodiments.

FIG. 5 illustrates a block diagram of an example entry for a printingdevice according to the disclosed embodiments.

FIG. 6 illustrates a block diagram of an example print job list in whichmultiple print jobs are routed to a plurality of printing devices inaccording to the disclosed embodiments.

FIG. 7 illustrates a flowchart of determining resources needed toperform print jobs in a print job list according to the disclosedembodiments.

FIG. 8 illustrates a flowchart of managing a print job list and printjob orders in a printing system according to the disclosed embodiments.

FIG. 9 illustrates a flowchart of managing print jobs in accordance withthe disclosed embodiments.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to specific embodiments of thepresent invention. Examples of these embodiments are illustrated in theaccompanying drawings. Numerous specific details are set forth in orderto provide a thorough understanding of the present invention. While theembodiments will be described in conjunction with the drawings, it willbe understood that the following description is not intended to limitthe present invention to any one embodiment. On the contrary, thefollowing description is intended to cover alternatives, modifications,and equivalents as may be included within the spirit and scope of theappended claims. Numerous specific details are set forth in order toprovide a thorough understanding of the present invention.

The disclosed embodiments include a printing system that routes andre-routes based on availability and capabilities of the printingdevices. A process just routing a job just as it is about to printedbased on the determined capabilities of a printing device still may notaddress the proper management within a system. It lets the user react tothe errors of the current print job without preparing the user forupcoming errors and warnings to minimize these problems from occurring.

Thus, the disclosed embodiments minimize the media-related errors thatcan happen by foreseeing which printing devices will need which papersizes and media types based on queued print jobs and priority printorder, if an order system also is in place. The disclosed embodimentsalso may use historical data indicating which printing devices canperform with less errors or paper jams for specific-type of print jobs.These features provide the user with useful information on which to actfirst to help in the efficiency of printing in a multiple deviceenvironment, or a printing system. For example, there may be a low paperwarning or a no paper error already in place but these do not give aninformed decision to operators or users on which warnings or errors toprioritize when working on multiple printing devices. The multipleprinting devices may share similar errors and warnings. A low paperwarning may be a higher priority notification than an empty tray errorif there is a pending job or order that will be fed from the “low paperwarning” tray than an empty tray with no pending print jobs.

FIG. 1 depicts a block diagram of a printing system 100 of a pluralityof printing devices, such as printing devices 104-116 coupled tomanaging server 102 that monitors and updates statuses of the pluralityof printing devices based on information received therefrom according tothe disclosed embodiments. System 100 includes printing devices 104-116and additional printing devices 150 connected to managing server 102 vianetwork 320. Printing devices 104 and 106 may be similar device models,while printing devices 108 and 110 also may be similar device modelsthat differ from printing devices 104 and 106. Printing device 116 maybe a different model altogether. Additional printing devices may beassociated with the different models. Further, system 100 may includeadditional models of printing devices not shown here for brevity.

A given printing device may be configured to perform one or morefunctions such as printing, scanning, emailing, storing, modifying,receiving, or transmitting one or more documents or files. In someembodiments, each printing device may include hardware and softwarecomponents associated with a firmware package. Firmware may refer topackages of software installed on embedded devices. Each firmware mayinclude a version for the different packages for the components withinthe printing device. A version of firmware, or firmware 312, may be sentfrom managing server 102 to one or more printing devices within system100.

Each printing device 104, 106, 108, 110, . . . , 116, and 150 may beconfigured to perform one or more steps, actions, or functions disclosedherein. For example, printing device 104 may communicate with managingserver 102 to transmit or receive data, or information, 322A via network320, including error codes, print counter values, time stamps, errorintervals, mean time between failures (MTBF), error frequency codes,time intervals, numbers of printed pages, numbers of errors, printvolume, remaining numbers or percentage of papers in paper cassettes,paper sizes in paper cassettes, toner levels, and other relatedinformation. Each printing device may send and receive its own datapackages, as shown in FIG. 1 . Data may be routed within system 100using a protocol, such TCP/IP, in that each device includes its ownunique network address. Thus, printing device 106 may transmit orreceive data 322B, printing device 108 may transmit or receive data324A, printing device 104B may transmit or receive data 324B, printingdevice 116 may transmit or receive data 326, and so on.

Managing server 102 may include a cloud-based server, for example, thatcan perform one or more tasks to manage or maintain printing deviceswithin system 100. Managing server 102 may communicate with printingdevices 104, 106, 108, 110, 116, and 150 to transmit and receive data.Managing server 102 also may install firmware 312 on one or more of theprinting devices. In some embodiments, managing server 102 may transmita command to one or more of the printing devices to reset, installupdates, or perform one or more printing or maintenance functions oroperations. In other embodiments, managing server 102 may receive datafrom one or more printing devices, shown as data 322A-326, such as errorcodes, print counter values, time stamps, error intervals, mean timebetween failures (MTBF), error frequency codes, time intervals, numbersof printed pages, remaining papers and paper sizes stored in papercassettes, numbers of errors, print volume, and other relatedinformation.

Managing server 102 may be configured to perform one or more functionsto determine whether to upgrade one or more printing devices withfirmware 312. Firmware 312 may represent a version of firmware that maybe used to replace one or more firmware packages on a set of printingdevices. For example, firmware 312 may be used to upgrade every printingdevice in system 100 or only a group of printing devices, such asdevices 104 and 106 having the same model. Managing server 102 performsthe analysis of incoming data from the printing devices to determinewhether to upgrade them with firmware 312. As noted above, firmware 312may be a firmware package corresponding to only a part of the printingdevice, such as main, network, or image processing. Failure rates andother information provided by the printing devices determines how or ifthe upgrade to firmware 312 will be sent or installed.

Managing server 102 may include one or more computing devices orsystems. It also may be consolidated into a single physical location ordistributed across two or more physical locations. Managing server 102may include hardware, software, or firmware configured to perform one ormore functions disclosed below. Managing server 102 is disclosed ingreater detail by FIG. 4 .

Network 320 in system 100 may include one or more wired or wirelessconnections that support communication between the devices of system100. In some embodiments, network 320 may support one or morecommunication protocols, such as Extensible Messaging and PresenceProtocol (XMPP), File Transfer Protocol (FTP), HyperText TransportProtocol (HTTP), Java Message Service (JMS), Simple Object AccessProtocol (SOAP), Short Message Service (SMS), Simple Mail TransferProtocol (SMTP), Simple Network Management Protocol (SNMP), TransmissionControl Protocol/Internet Protocol (TCP/IP), User Datagram Protocol(UDP), Lightweight Directory Access Protocol (LDAP), and the MessageQueue (MQ) family of network protocols.

Network 320 is configured to allow communication between managing server102 and one or more printing devices within system 100, between theprinting devices themselves, or between one or more other devices orsystems and system 100. Such communications may include commands,requests, or data corresponding to documents, printing-device errors, orother data.

More details of printing system 100 of FIG. 1 are depicted in FIG. 2 .In FIG. 2 , only printing devices 104, 106, 108, 110, 112, 114, 116, and118 are illustrated in printing system 100. Additional printing devicesmay be included in printing system 100. Alternatively, fewer printingdevices may be utilized. As described above with reference to FIG. 1 ,printing devices 104-118 are connected over a network within system 100to a printing system managing server 102. Managing server 102 may storeinformation and data pertaining to the different printing devices.Managing server 102 also may collect this information and make decisionsregarding the workflow and error priority of the printing device insystem 100. An exemplary printing device is disclosed in a greaterdetail by FIG. 3 . Managing server 102 is disclosed in greater detail inFIG. 4 .

The disclosed embodiments aim to prevent or minimize the down time ofthe printing devices 104-118 by helping users of printing system 100 toplan ahead for the immediate paper size and media type needed forcurrent and queued print jobs. Printing system 100, using managingserver 102 or another device, may query all the managed printing devicesfor paper cassette statuses and other job halting errors. It also maysubscribe to status changes for the paper cassettes and device errors.Printing system 100 may gather information on pending print jobs foreach printing device, such as paper sizes used, number of pages in thepending print jobs, number of copies, media types used, and the like.Printing system 100 also may gather information on pending job ordersnot yet started to be printed. It also may gather historical, or dataanalyses, information, such as paper sizes and media types used whetherfor printing or waste-like jams, time to replenish paper cassettes, timeto consume toner, cleaning fluid, and the like, time for a waste bottleto be replaced, and the like. The disclosed embodiments may determineand give weight to each error or warning event that would dictate thepriority of the error or warning as well as displaying a prioritizedlist to users.

When multiple errors or warnings are detected from multiple printingdevices, printing system 100 may utilize all the gathered informationdisclosed above to prioritize the errors and warnings accordingly.Printing system 100 also may notify the user of the priority so each onecan be addressed efficiently. It will prioritize the errors and warningsaccording to active pending print jobs but printing system 100 also canconsider delivery dates of pending job orders not yet started to beprinted. Alternatively, it may prioritize based on the time it takes toresolve any errors or warnings. Printing system 100 also may anticipatelow paper or empty cassette warnings based on queued print jobs orpending print job orders. Printing system 100 also may notify or suggestto users to reload or the change unused cassettes to feed needed papersizes or media types based on demand so that a printing device mayprocess print jobs with no or little interruption. Because printingsystem 100 is subscribing to changes in printing device status,prioritized lists of errors or warnings are updated on the fly, or inreal-time.

These features may be implemented in managing server 102. Managingserver 102 may communicate with the various printing devices to collectsuch information in order to provide management of print jobs withinprinting system 100 according the disclosed embodiments. The informationcollected from various printing devices may be stored as an entry foreach printing device, such as entry 130 shown in FIG. 1 , which will bedescribed in greater detail in FIG. 5 . In other embodiments, printingsystem 100 may not include a server but, instead, perform the processdisclosed herein at one or more printing devices within the system. Asdisclosed below, printing system 100 and managing server 102 aredescribed interchangeably performing functions and processes to manageprinting devices 104-118.

Print jobs may be received by printing system 100. In some embodiments,managing server 102 may determine which printing device receives eachprint job. For example, managing server 102 may determine that printingdevice 104 does not receive every print job received in the printingsystem. Further, a print job may specify a certain type of paper ormedia type that is only available on certain printing devices. Forexample, a print job may require the use of A4 sized paper, which isonly available on printing device 106 and 116. Thus, it would make nosense to send this print job to printing device 108, which onlyprocesses print jobs using letter sized paper.

In addition to managing print jobs based on capabilities of the printingdevice, the disclosed embodiments also manage print jobs according todevice status information, pending job information, error information,warning information, and historical information from each of theprinting devices within printing system 100. These features aredisclosed in greater detail below. Managing server 102 may store thisinformation for each printing device as data entries 130 in a database.

For example, there may be an entry 130 for information for printingdevice 104, an entry 130 for information for printing device 106, anentry 130 for information for printing device 108, and so on. Printingsystem 100 may retrieve relevant information from the printing devicesbeing managed. This information includes information about the printingdevice and information about the jobs being processed in the printingdevice. Device information may include information such as papercassette statuses, ink level status, cleaning media types set percassette, media sizes per cassette, cleaning fluid, waste bottle levels,paper jams, device system errors, output bin statuses, stapler status,and the like. Printing system 100 also may retrieve pending print jobstatus information from each printing device liking printing inprogress, incoming print job(s), suspended print job(s), user inputrequired, and the like.

Printing system 100 may establish a subscription 134 on each printingdevice for device and print job statuses. Subscription 134 is shown inprinting device 116 but also may be available on the other printingdevices in system 100. Subscription 134 may provide updates andinformation to managing server 102. When a status change occurs for theprinting device or print jobs, the applicable printing device sends anotification 136 to printing system 100. For example, referring toprinting device 116, the status of paper cassette 1 may change from lowpaper to empty cassette. Printing device 116 sends notification 136 tothis effect. Printing system 100 may evaluate notification 136 and savethe current information in entry 130 for information for printing device116 on managing server 102. Printing system 100 also may createhistorical data for printing device 116 that will be used for dataanalytics. When notification 136 received from a printing deviceindicates a device error or status that caused the device to stopprinting, printing system 100 may escalate this notification as ahighest priority error.

Printing system 100, using managing server 102, may parse print jobs 140in print queue 138 for a printing device. Referring back to printingdevice 116, print queue 138 is shown with four (4) pending print jobs140. Print jobs 140 may include print job 1, print job 2, print job 3,and print job 4. The disclosed embodiments may parse print jobs 140 forjob settings such as a number of copies, paper sizes, media types,number of pages, duplex, Nup, booklet, staple, and the like. Forexample, if duplex is set, then the number of media sheets needed arecomputed from the number of pages divided by 2 for front-sheet printingand back-sheet printing. This feature determined the needed resourcesper queued print job.

The disclosed embodiments also may determine if resources needed by aqueued print job, such as print job 1 of print jobs 140 for printingdevice 116, will cause the printing device to stop printing given thecurrent device status, such as paper level, ink level, media type, sizesloaded in the cassettes, and the like. Printing operations may stop dueto inadequate paper resources or other resources such as staples, ink,space in the output bit, and the like. This determination may beperformed for all pending print jobs 140 in print queue 138. Theevaluation of a particular queued print job may take into accountresources that will be consumed by all ahead-of-the-line queued printjobs 140 to foresee if it will cause an error. When a new status updateis received from a printing device, the list of pending print jobs ororders, which has information already on their needed resources, may bereevaluated to determine if the new status will cause an error or awarning.

The disclosed embodiments also determine the overall priority of errorsor warnings on printing devices within printing system 100. If queuedprint jobs 140 will cause an error or warning, the priority of the newerror or warning also is determined. The priority of error or warningsmay rank these items using the error categories disclosed below. Theseerror categories may differ between printing systems. Printing system100 may determine a priority of errors and warnings across all printingdevices as well as within each printing device. Thus, printing system100 may analyze print queues 138 on all printing devices as well as theone on printing device 116. The errors and warnings also may beprioritized based on print job order. In a preferred embodiment, theerrors and warnings may be sent to managing server 102 and saved inrespective device information entries 130.

There are several categories of the priority problems according to thepreferred embodiments. The highest priority problems may be referred toas ERRORS. ERRORS include print-halting errors and statuses that requireimmediate user attention for printing operations to proceed. Such errorsinclude paper jams, empty paper cassettes, missing output cassettes,open device cover or door, user input is required on the printingdevice, and the like. The information for these problems is retrievedfrom the printing device or automatically sent by the printing device toprinting system 100 or managing server 102 when processing a currentprint job. Preferably, subscription 134 is provided on the printingdevice to enable the automatic reporting of an ERROR when it occurs.

Potential print-halting errors may be the second highest priority. Thiscorrelates the print jobs resource demand versus the printing devicesresource supply. These problems may be referred to as POTENTIAL ERRORS.When queued print job N, such as print job 1, 2, 3, or 4 in print queue138 of printing device 116, definitely cannot be printed with thecurrent resources from the printing devices, it will have POTENTIALERROR priority N. For example, the problem may relate to missing papersize, missing media type, and the like. For the same case queued printjob N+1, it will be POTENTIAL ERROR priority N+1, and so on.

The following example referring to printing device 116 may beillustrative. For estimated statuses like the amount of paper availablein percentage, an error threshold is set to determine when this statusis considered an error. Information for the capacity per paper feedermay be retrieved from printing device 116 and stored as an entry 130 atmanaging server 102. Using the example, a cassette sends a 50% paperavailable status for a 500-sheet paper cassette, which equates toapproximately 250 sheets left on the cassette. An error threshold may beset to 20%, which indicates printing device 116 can print 20% more thanthe estimated sheets left before it can be considered an error due to anempty cassette. Thus, if a print job needs 300 sheets or more, then itis considered a POTENTIAL ERROR based on the information indicating 50%available paper and a 20% error threshold.

Third highest priority problems may be referred to HIGH-PRIORITYWARNINGS. This situation occurs when a queued print job can potentiallycause a print-halting error. A warning threshold is set to determinewhen it is considered to a cause a print-halting error. As disclosedabove, some statuses or warnings from a printing device may just beestimates. For example, a cassette sends out a low paper warning status.Such a status may be defined as having about 20% left of the relevantpaper. For a 500-sheet paper cassette having a low paper warning, or 20%left, the paper cassette has about 100 sheets left on its cassette. Ifthe warning threshold is set to 20%, then 80 sheets or less isconsidered “safe” from printing on a cassette with a low paper status.If one or more print jobs need more than 80 sheets to be printed, thenthis situation may be considered a HIGH-PRIORITY WARNING.

Fourth highest priority problems may be referred to as MEDIUM-PRIORITYWARNINGS. These may be device errors that have no relations with queuedprint jobs. For example, empty cassette errors with no print job needingto feed from that cassette may be MEDIUM-PRIORITY WARNINGS. As soon asprint jobs are lined up for that printing device and needs the emptycassette, the priority escalates to either a HIGH-PRIORITY WARNING or aPOTENTIAL ERROR.

Fifth priority problems on the priority list may be referred asLOW-PRIORITY WARNINGS. As same as the fourth priority problems, thefifth priority problems are not relative to the queued print jobs andcan be device warnings, such as low paper but no lined up jobs, lowtoner, etc. As soon as print jobs are lined up for that printing deviceand needs more papers than what it has, the priority escalates to eithera HIGH-PRIORITY WARNING or a POTENTIAL ERROR.

Examples for managing the queued print jobs based on the priority levelswill be described in detail below with reference to FIGS. 5-9 .

FIG. 3 depicts a block diagram of components of a printing deviceaccording to the disclosed embodiments. In the disclosure of FIG. 3 ,printing device 104 may be referred to for illustrative purposes. Thearchitecture shown in FIG. 3 may apply to any multi-functional printingdevice or image forming apparatus that performs various functions, suchas printing, scanning, storing, copying, and the like within printingsystem 100. As disclosed above, printing device 104 may send and receivedata from managing server 102 and other devices within system 100.

Printing device 104 includes a computing platform 201 that performsoperations to support these functions. Computing platform 201 includes acomputer processing unit (CPU) 202, an image forming unit 204, a memoryunit 206, and a network communication interface 210. Other componentsmay be included but are not shown for brevity. Printing device 104A,using computing platform 201, may be configured to perform variousoperations, such as scanning, copying, printing, receiving or sending afacsimile, or document processing. As such, printing device 104 may be aprinting device or a multi-function peripheral including a scanner, andone or more functions of a copier, a facsimile device, and a printer. Toprovide these functions, printing device 104 includes printer components220 to perform printing operations, copier components 222 to performcopying operations, scanner components 224 to perform scanningoperations, and facsimile components 226 to receive and send facsimiledocuments. CPU 202 may issue instructions to these components to performthe desired operations.

Printing device 104 also includes a finisher 211 and one or more papercassettes 212. Finisher 211 includes rotatable downstream rollers tomove papers with an image formed surface after the desired operation toa cassette. Finisher 211 also may perform additional actions, such assorting the finished papers, binding sheets of papers with staples,doubling, creasing, punching holes, folding, and the like. Papercassettes 212 supply paper to image the various components 220, 222,224, and 226 to create the image formed surfaces on the papers. Papercassettes 212 may include papers having various sizes, colors,composition, and the like. Paper cassettes 212 may be removed to refillas needed.

Document processor input feeder cassette 230 may be the physicalcomponents of printing device 104 to receive papers and documents to beprocessed. A document is placed on or in document processor input feedercassette 230, which moves the document to other components withinprinting device 104. The movement of the document from documentprocessor input feeder cassette 230 may be controlled by theinstructions input by the user. For example, the document may move to ascanner flatbed for scanning operations. Thus, document processor inputfeeder cassette 230 provides the document to scanner components 220. Asshown in FIG. 2 , document processor input feeder cassette 230 mayinteract with engine firmware 260 to perform the desired operations.

Memory unit 206 includes memory storage locations 214 to storeinstructions 215. Instructions 215 are executable on CPU 202 or otherprocessors associated with printing device 104, such as any processorswithin components 220, 222, 224, or 226. Memory unit 206 also may storeinformation for various programs and applications, as well as dataspecific to printing device 104. For example, a storage location 214 mayinclude data for running an operating system executed by computingplatform 201 to support the components within printing device 104.According to the disclosed embodiments, memory unit 206 may store thetokens and codes used in performing the deferral operations for printingdevice 104.

Memory unit 206 may comprise volatile and non-volatile memory. Volatilememory may include random access memory (RAM). Examples of non-volatilememory may include read-only memory (ROM), flash memory, electricallyerasable programmable read-only memory (EEPROM), digital tape, a harddisk drive (HDD), or a solid-state drive (SSD). Memory unit 206 alsoincludes any combination of readable or writable volatile memories ornon-volatile memories, along with other possible memory devices.

Computing platform 201 may host one or more processors, such as CPU 202.These processors are capable of executing instructions 215 stored at oneor more storage locations 214. By executing these instructions, theprocessors cause printing device 104 to perform various operations. Theprocessors also may incorporate processing units for specific purposes,such as application-specific integrated circuits (ASICs) and fieldprogrammable gate arrays (FPGAs). Other processors may be included forexecuting operations particular to components 220, 222, 224, and 226. Inother words, the particular processors may cause printing device 104 toact as a printer, copier, scanner, and a facsimile device.

Printing device 104 also includes an operations panel 208, which may beconnected to computing platform 201. Operations panel 208 may include adisplay unit 216 and an input unit 217 for facilitating interaction witha user to provide commands to printing device 104. Display unit 216 maybe any electronic video display, such as a liquid crystal display (LCD).Input unit 217 may include any combination of devices that allow usersto input information into operations panel 208, such as buttons, a touchscreen, a keyboard or keypad, switches, dials, and the like. Preferably,input unit 217 includes a touch-screen digitizer overlaid onto displayunit 216 that senses touch to receive inputs from the user. By thismanner, the user interacts with display unit 216. Using thesecomponents, one may enter codes or other information into printingdevice 104.

Printing device 104 also includes network communication processing unit218. Network communication processing unit 218 may establish a networkcommunication using a network, such as a wireless or wired connectionwith one or more other image forming apparatuses or managing server 102.CPU 202 may instruct network communication processing unit 218 totransmit or retrieve information over a network using networkcommunication interface 210. As data is received at computing platform201 over a network, network communication processing unit 218 decodesthe incoming packets and delivers them to CPU 202. CPU 202 may actaccordingly by causing operations to occur on printing device 104. CPU202 also may retrieve information stored in memory unit 206, such assettings for printing device 104.

Printing device 104 also includes engine 260. Engine 260 may be acombination of hardware, firmware, or software components that actaccordingly to accomplish a task. For example, engine 260 is comprisedof the components and software to print a document. It may receiveinstructions from computing platform 201 after user input via operationspanel 208. Alternatively, engine 260 may receive instructions from otherattached or linked devices.

Engine 260 manages and operates the low-level mechanism of the printingdevice engine, such as hardware components that actuate placement oftoner onto paper. Engine 260 may manage and coordinate the half-toner,toner cartridges, rollers, schedulers, storage, input/output operations,and the like. Raster image processor (RIP) firmware 290 that interpretsthe page description languages (PDLs) would transmit and sendinstructions down to the lower-level engine 260 for actual rendering ofan image and application of the toner onto paper during operations onprinting device 104.

In some embodiments, managing server 102 may send updates to firmware onprinting device 104. Thus, engine 260 or RIP firmware 290 may be updatedby a firmware, for example, firmware 312 shown in FIG. 3 , which is amore recent version of the firmware installed on printing device 104.The installation of the new firmware version, however, may result inadditional errors or degradation of performance of printing device 104.In this instance, printing device 104 may not install firmware 312.

To this end, printing device 104 may include one or more sensors 262(only four are shown in the figure for brevity) that collect data andinformation to provide to computing platform 201 or CPU 202. Each sensor262 may be used to monitor certain operating conditions of printingdevice 104. Sensors 262 may be used to indicate a location of a paperjam, failure of hardware or software components, broken parts, operatingsystem problems, document miss-feed, toner level, number of papersremained in the paper cassettes, as well as other operating conditions.Sensors 262 also may detect the number of pages printed or processed byprinting device 104. When a sensor 262 detects an operational issue orfailure event, it may send a signal to CPU 202. CPU 202 may generate anerror alert associated with the problem. The error alert may include anerror code. Computing platform 201 may transmit the error alert alongwith the error code to managing server 102. Further, sensors 262 maydetect the paper size, a percentage of paper remained, a toner level andso on, and send the detection results to computing platform 201.Computing platform 201 in turns sends the results to managing server 102upon request or automatically.

Display unit 216 may display information about applicable error codesand a short description of the error associated with the operationalissue or failure event. Further, display unit 216 may display aninstruction on how to proceed (operate) to resolve the error. Forexample, if a network error occurred, then the following message may beprovided on operations panel 208: Reboot the device.

Some errors have hardware-related causes. For example, if a failureoccurred in finisher 211, such as a paper jam, display unit 216 maydisplay information about the error and the location of the failureevent, or the finisher. In the instance when the paper jam occurs inpaper cassettes 212, display unit 216 displays the information about thejam error as located in one of the paper cassettes.

Some errors have a type of firmware-related cause. For example, networkcommunication processing unit 218 may cause a firmware or softwareerror. Display unit 216 may display the firmware-related error, anyapplicable error codes, and provide recommendations to address theerror, such as reboot the device.

Memory unit 206 may store the history of failure events and occurrederrors with a timestamp of each error. The history of failure events maybe sent via network communication interface 210 to managing server 102for statistical purpose. Printing device 104 communicates with managingserver 102 via network communication interface 210 by utilizing anetwork protocol. In some embodiments, printing device 104 communicateswith managing server 102 through REST API, which allows the server tocollect data from multiple devices via network 320 (shown in FIG. 3 ).REST API and SOAP are application protocols used to submit data indifferent formats, such as files, XML messages, JSON messages, and thelike. By utilizing applicable network communication protocols andapplication protocols, printing device 104 submits the applicable errorcode or codes to managing server 102. Managing server 102 collects errorcodes and data from individual devices, stores information in thedatabase for further analysis, and creates information data entries(e.g., 130 of FIG. 1 ) for individual printing devices. The data storedin the database includes device identification, timestamp, error code,remaining number or percentage of papers, paper size, and the like.

According to preferred embodiments of the present invention, afteranalyzing the collected information from individual printing devices,managing server 102 distributes different printing jobs received from anetwork to different printing devices based on the collectedinformation, and re-directs printing jobs to a different printing devicewhen detecting an error or warning from an assigned printing device. Thedetails of managing server 102 will be described in detail below withreference to FIGS. 3-4 .

FIG. 4 depicts a block diagram of managing server 102 according to thedisclosed embodiments. The components of managing server 102 mayinclude, but are not limited to, one or more processors or processingunits 430 and a server memory 432. A server bus 434 couples variousserver components including server memory 432 to processor 430. Managingserver 102 may include a variety of computer readable media. Such mediamay be selected from any available media that is accessible by managingserver 102, including non-transitory, volatile, and non-volatile media,removable and non-removable media. Server memory 432 could include oneor more personal computing readable media in the form of volatilememory, such as random access memory (RAM) 436 or a cache memory 438. Insome embodiments, a storage system 440 may be provided for reading fromand writing to a non-removable, non-volatile magnetic media device, suchas a hard drive.

Server memory 432 may include at least one program product or utility442 having a set, or at least one, of program modules 444 that may beconfigured to perform the functions of the disclosed embodiments.Program modules 444 may include, but are not limited to, an operatingsystem, one or more application programs, other program modules, andprogram data. Each of the operating systems, one or more applicationprograms, other program modules, and program data or some combinationthereof, may include an implementation of a networking environment.Program modules 444 may perform the functions or methodologies ofembodiments of the invention as disclosed herein. For example, a programmodule 444 in managing server 102 may be configured to determine ifcomponents of one of the printing devices of system 100 needs to bereplaced or fixed due to a failure event, error, or warning within thedevice.

Managing server 102 may communicate with one or more external devices446, such as a keyboard, a pointing device, a stylus, a display 448, orany similar devices, such as a network card, modem, and the like.Display 448 may be a light emitting diode (LED) display, a liquidcrystal display (LCD) display, a cathode ray tube (CRT) display, and thelike. External devices 446 may enable managing server 102 to communicatewith a printing device. Such communication may occur via input/output(I/O) interfaces 450. Alternatively, managing server 102 may communicatewith one or more networks such as a local area network (LAN), a generalwide area network (WAN), or a public network via a network adapter 452.Managing server 102 may be coupled to a network via a wired or wirelessconnection. Network adapter 452 may communicate with the othercomponents via bus 434.

Any combination of one or more computer readable media, for example,storage system 440, may be utilized. In the context of the disclosedembodiments, a computer readable storage medium may be any tangible ornon-transitory medium that contains, or stores, a program, such asprogram product 442, for use by or in connection with an instructionexecution system, apparatus, or device. A computer readable storagemedium may be, for example, but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,or device, or any suitable combination of the foregoing.

In some embodiments, managing server 102 may release firmware 312, whichis an upgrade to existing firmware on one or more printing deviceswithin system 300. Firmware 312 may be forwarded to one or more printingdevices through network adapter 452 when instructed by processing unit430. Processing unit 430 may execute instructions stored in servermemory 432 to configure managing server 102 to perform the steps andfunctions disclosed below. Specifically, instructions stored in programmodules 444 may determine whether to upgrade firmware within theplurality of devices in system 300.

As illustrated in FIG. 2 , information about each printing device104-116 is stored in an entry, such as entry 130. Entry 130 may bereferred by managing server 102 to control and manage print jobs sent toprinting devices 104-116. The information saved in entry 130 may beupdated by printing devices 104-116 sending their statuses to managingserver 102 automatically, periodically, in real time, or upon request ofmanaging server 103 or system 100. In FIG. 2 , entries 130 are saved inmanaging server 102. Entries 130, however, may also be saved in aseparate database without limitation.

FIG. 5 depicts information, but not limited to, included in an exemplaryentry 130 of individual printing devices 104-118 in accordance with thepreferred embodiments. It is noted that the information illustrated inFIG. 5 is for exemplary purpose. Other information about printing devicestatus may be added as needed. Entry 130 may be created by printingsystem 100 and includes various information about printing devices104-118, such as warning status, priority status, error status, firmwareinformation, and so on. Entry 130 may be stored in a database, such asstorage 440 of managing server 102. Changes of information in entry 130can be sent to entry 130 automatically or in request by printing systemto update the information of entry 130. Based on information of entry130, managing server 102 monitors the statuses of each printing device104-118 and controls printing job list accordingly.

Firmware information 502 includes information about firmware version,type of firmware, date of installation, and so on. In some situation,managing server 102 may update firmware to a specific printing device sothat this specific printing device is capable of performing a print jobsent from system 100. After a new firmware is installed in the specificprinting device, the information of the firmware version, type offirmware and date of installation will also be updated.

Error history 504 records dates of error occurrences and their codes.Based on the error history, managing server 102 can decide if thisspecific printing device is suitable for printing a specific job. Forexample, on Jan. 1, 2020, an error code of paper jam occurred at aprinting device after the printing device prints 100 pages of adocument. Same error code of paper jam occurred again in Jan. 3, 2020.Managing server 102 thus will not direct a print job that uses more than100 papers to this specific printing device on Jan. 5, 2020 unless suchan error code has not been recorded for a certain period of time, e.g.,one month. The error codes may also include toner drum errors,power-interrupted errors, and so on.

The error codes also may be correlated with an “age” of the printingdevices. The age of a printing device may be indicated by a total printvolume. Some devices may print up to several million pages during theirlifetimes. For instance, some devices that have a low level of totalprint volume may be affected by specific error or failure events ascompared to those devices having a high total print volume. Hardwarecomponents may start to break down to result in failure events or errorsat a certain “age” or print volume. Thus, managing server 102 mayreceive data from the printing devices on their total print volume.Alternatively, managing server 102 may determine average print volumesfor the periods used to determine failure rates and MTBFs for errorcodes and printing devices.

Print volume history 506 includes at least information regarding printto volume count, date of check out, etc. Those information helpsmanaging server 102 to decide if the printing device is out-of-date toexecute a specific print job.

Paper cassette information 508 includes a number (or percentage) ofpapers remaining in a paper cassette. There may be more than one papercassette in a printing device. Thus, the paper cassette information 508may include cassette number and its relative data. Other than the number(percentage) of remaining papers, paper cassette information 508 mayalso include information of paper sizes, paper quality, paper thickness,media type, cleanness level, paper jam information, and so on. Further,ink toner information 510 includes information relating to remaining inklevel, color/black-and-white ink cartridge, etc. Managing server 102 maydirect a print job that needs color and B5 paper size to a printingdevice that can accommodate such features based on the paper cassetteinformation 508 and ink toner information 510 stored in entries 130.Details of how managing serve 103 directs and redirects print jobs willbe described later.

According to the preferred embodiments, managing server 102 may redirecta print job that is originally sent to a first printing device to asecond printing device when a warning or error signal is received fromthe first printing device. Warning information 512 indicates whether theprinting device has a High-Priority warning, a Medium-Priority Warning,or a Low-Priority warning. Error information 514 indicates that theprinting device has an Error, or a Potential Error. Different levels ofwarnings and errors have been described above with reference to FIG. 2and thus no further explanations are needed here for brevity.

Entry 130 may also include priority job information 516. Priority jobinformation 516 indicates that the job number assigned to the printingdevice, whether this job number is in progress, incoming job number,suspending job number, and so on. The status of each print job may beindicated.

Based on the information stored in entries 130 of printing devices104-118, the disclosed embodiments allow a list of print jobs to bedirected or redirected to suitable printing devices. For example,managing server 102 determines a print job for printing device 116 willstop printing given the situation that printing device 116 does not haveenough paper in its cassette 1 based on a POTENTIAL WARNING receivedfrom printing device 116. Managing device 102 may then send a signal toa user to add more papers into cassette 1, or redirects the print job toanother printing device, such as printing device 114, based on the timeof the day or other conditions.

Examples of how managing server 102 directs and redirects print jobs tovarious printing devices based on entries 130 is illustrated in FIG. 6 .

According to the preferred embodiments, when working on a singleprinting device and when errors and warnings are displayed based onresolving issues per printer, summary of inadequate resources inprocessing N number of jobs for the printer may be sent to entries 130of this printing device. In response, managing device may send theinformation to a user of the printing device so that the user can workon replenishing the resources to process N number of jobs, i.e., notjust mitigating the obvious error reported for the current job as canalready be seen in the printing device's display panel. This in effectavoids repetitive interruption on the printing device. It also gives theuser the option to make the most out of interruption.

When working on multiple devices, such as printing devices 104-118 ofFIG. 2 , the whole fleet of printing devices in the user's location maybe theoretically considered as one big printing device. Inadequateresources for printing the queued print jobs, despite having multipleprinters, is still identified. When a printing device needs userattention, the display of errors and warnings can again summarize alllacking resources (sorted based on job order) to process the print jobs,and user can “refill” those resources to resolve one or more print jobresource/media needs. Alternatively, managing server 102 may re-directsome print jobs to other suitable printing devices. This is particularlyimportant when the errors or warnings occur at time when the user is notworking.

FIG. 6 illustrates an exemplary diagram for routing jobs of a print joblist in accordance with the preferred embodiments. In FIG. 6 , printingdevices 1-3 are used to execute print jobs shown in job list 610.Printing device 1 has three paper cassettes: cassette 1 has plain A4size papers, cassette 2 has plain letter size papers, and cassette 3 hasplain A3 size papers. Printing device 2 also contains three cassettes:cassette 1 has high quality A5 size papers, cassette 2 has high qualityA4 size papers, and cassette 3 has colored letter sized paper. Inprinting device 3, cassette 1 has plain statement size papers, cassette2 has plain A3 size papers, cassette 3 has high quality letter sizepaper, and cassette 4 has plain A4 papers. The jobs in job list 610includes Jobs 1-8. Job 1 requires plain A4 size papers. Job 2 requiresprinting on letter size papers and colored. Job 3 requires A3 sizepapers and colored. Job 4 requires high quality A4 paper. Job 5 requiresthick A4 papers. Job 6 requires A3 size plain papers. Job 7 requiresplain letter size papers, and Job 8 requires high quality A5 sizepapers.

As shown in FIG. 6 , Jobs 1, 6, and 7 are sent to printing device 1,Jobs 2, 4, and 8 are sent to printing device 2, and Jobs 3 and 5 aresent to printing device 3 for processing. As printing device 3 does nothave A3 color paper in its cassettes, “Load A3 Color” instructions willbe displayed on its display panel. Also, since system 100 knows that Job5 cannot be printed in printing devices 1 and 2, system 100 will suggestprinting device 3 for Job 5 as it has “unused” cassette (cassette 1)that can be changed to feed A4 thick papers. Accordingly, printingdevices 1 and 2 are able to execute printing jobs sent to them withoutinterruption. Jobs 3 and 5 can be printed with only one interruption.

The disclosed preferred embodiments also allow managing server 102 toreceive update information from printing devices 1-3, such as the amountof the papers in cassette 1 of printing device 1 is running low (forexample, a POTENTIAL ERROR, ERROR, HIGH-PRIORITY WARNING,MEDIUM-PRIORITY WARNING, or a LOW-PRIORITY WARNING, based on therespective settings.) In this case, managing server 102 may send anotification to the user to load more A4 size plain papers, or redirectJobs 1 to printing device 3. Managing server 102 may again re-direct Job1 back to printing device 1 when the papers in cassette 4 of printingdevice 1 are also running low and more papers in cassette 1 of printingdevice 1 have been loaded. This determination may be performed for allpending print jobs 1-8 in print job list 610. The evaluation of aparticular queued print job may take into account resources that will beconsumed by all ahead-of-the-line queued print jobs to foresee if itwill cause an error. When a new status update is received from aprinting device, the list of pending print jobs or orders, which hasinformation already on their needed resources, may be reevaluated todetermine if the new status will cause an error or a warning.

Further, if queued print jobs 1-8 will cause an error or warning, thepriority of the new error or warning also is determined. The priority oferror or warnings may rank these items using the error categoriesdisclosed in FIG. 2 . These error categories may differ between printingsystems. Printing system 100 or managing server 102 may determine apriority of errors and warnings across all printing devices as well aswithin each printing device. Thus, printing system 100 may analyze printjob list 610 on all printing devices. The errors and warnings also maybe prioritized based on print job order. In a preferred embodiment, theerrors and warnings may be sent to managing server 102 and saved inrespective device information entries 130.

History data gathered from device statuses can also be used asadditional information for managing server 102 to determine routingdecisions. For example, printing device 1 has 20% chance of paper jamwhen processing A4 Thick media types, while printing device 2 has 5%chance of paper jam for A4 Thick media types. Accordingly, when a printjob of A4 Thick media types is requested, system 100 or managing server102 will suggest printing device 2 to load A4 Thick papers and directthe print job to printing device 2 instead of printing device 1.

Firmware information stored in entry 130 can also be used to determinewhere a print job to route to. For example, when a firmware version/typeof printing device 2 is an old version that cannot process Job 4,managing server 102 may download an updated firmware to printing device2 or redirect Job 4 to other capable printing device.

FIGS. 7-9 depict flowcharts for determining print job resources based onstatuses of multiple printing devices in accordance with the disclosedembodiments. FIG. 7 depicts a block diagram for prioritizing statusinformation collected from multiple printing devices in accordance withthe disclosed embodiment. FIG. 8 depicts a block diagram for managingprint jobs sent to multiple printing devices based on statusesinformation collected from the multiple printing devices. FIG. 9 depictsa block diagram for managing a print job list sent to multiple printingdevices in accordance with the disclosed embodiments.

FIG. 7 depicts a flowchart 700 for prioritizing status informationcollected from a multiple of printing devices in accordance with thedisclosed embodiment. Printing system 702 comprises a multiple ofprinting devices 1, 2, . . . , N for executing a list of print jobs.Printing system 702 may be printing system 100 of FIGS. 1-2 and printingdevices 1, 2, . . . , N may be printing device 104-118 of FIGS. 1-3 .

Step 702 executes by printing system 100 or managing server 102 (shownin FIGS. 1-4 ) collecting information of each of printing devices 1, 2,. . . , N including device status updates. As described above, printingsystem 100, using managing server 102 or another device, may query allthe managed printing devices for paper cassette statuses or otherhalting errors. The printing devices may also subscribe to send statuschanges for paper cassettes and device errors. Information gathered byprinting system 100 may include information on pending print jobs foreach printing device, such as paper sizes used, number of pages in thepending print jobs, number of copies, media types used, and the like,and information on pending job orders not yet being printed. Theinformation may further include historical, or data analyses,information, such as paper sizes and media types used whether forprinting or waste-like jams, time to replenish paper cassettes, time toconsume toner, cleaning fluid, and the like, time for a waste bottle tobe replaced, and the like. All the above information gathered byprinting system 100 are saved in respective entry of each printingdevice in storage 710.

Steps 706 and 708 execute by saving current statuses of each printingdevice 1, 2, . . . , N and gathering and saving data analyticsinformation obtained based on the current statuses to storage 710.Storage 710 may be memory 206 of printing system 100 or storage system440 of managing server 102, or a separate database. Information relatedto each printing devices 1, 2, . . . , N is stored in their respectiveentries (such as entries 130). Printing system 100 or managing server102, by referring to information saved in the entries, determine orforesee print job list orders that make best use of resources withminimum interruption.

The status updates of each printing device may be sent to printingsystem in real time or by request. Upon receiving the status updates ofeach of printing devices 1, 2, . . . , N at step 704, printing system100 or managing server 102 determines if the status updates of aprinting device will result in device errors or warnings for thisprinting device, as executed at step 710. Types of device errors andwarnings and their priority levels have been described in the preferredembodiments of FIG. 2 , and detailed descriptions thereof are omittedfor brevity. If the answer is Yes, step 712 executes by determining ifthe device errors or warnings will cause this printing devices to stopfunctioning.

If the answer of step 712 is Yes, step 714 executes by placing thedevice errors and warnings at highest priority weight. If the answer ofstep 812 is No, the process goes to step 716 for determining priority ofthe device errors/warnings. Step 718 executes by displaying anerror/warning notice on a display panel of the printing devices. Next,step 720 executes by printing system 100 or managing server 102determining best suggestions based on data analytics informationobtained at step 708 and displaying such suggestions on the displaypanel of the printing device.

FIG. 8 depicts a flowchart 800 for determining suitable resources forperforming print jobs in a print job list and a print order list inaccordance with the preferred embodiments. When a print job list 802 anda print order list 804 are presented, printing system 100 or managingserver 102 determines if any print jobs exist in the print job list 802,at step 806, and any priority print order exists in print order list804, at step 808.

At step 806, if there is no print job existed in print job list,printing system 100 or managing server 102 determines if any priorityprint orders are existed in print order list 804. When there are printjobs existed in print job list 802, step 810 executes by printing system100 or managing server 102 parsing print jobs and determining suitablesources for the print jobs. In accordance with the preferredembodiments, printing system 100 or managing server 102 may refer toinformation stored in storage 710 and current statuses of the printingdevices at step 830 to decide which printing devices are neededresources for executing the print jobs. Similarly, when there ispriority print order exists at step 808, step 812 executes by printingsystem 100 or managing server 102 parsing print jobs in the print orderand determining which printing devices are needed resources forexecuting the print jobs based on information stored in storage 710 andthe current statuses of the printing devices.

Step 814 executes by printing system 100 or managing server 102 savingand refreshing the list of print jobs and their associated resourceneeds after the determinations at steps 810 and 812 are made. Next, step816 executes by printing system 100 or managing serve 102 determining ifeach print job/order according to their order will cause an error or awarning by referring data analytics information 832 obtained byanalyzing information saved in storage 710 and the current statuses ofthe printing devices.

At step 818, if the print job/order will cause an error or a warning,step 818 executes by determining a priority of the error/warning. Step820 executes by displaying such an error/warning on a display panel of arelated printing device. Further, step 822 executes by printing system100 or managing server 102 making suggestions on how to solve theerror/warning, based on data analytics information 832, and displayingsuch suggestions on the display panel of the related printing device. Insome preferred embodiments, printing system 100 or managing server 102may further redirect the print job that will cause an error or warningfor a first printing device to a second printing device that canaccommodate this print job, as shown at step 826.

FIG. 9 depicts a flowchart 900 for redirecting a print job to a suitableprinting device in accordance with the preferred embodiments.

Step 902 executes by printing system 100 receiving a print job list.Step 904 executes by printing system 100 parsing print jobs in the printjob list and determining needed resources for individual print job. Thedetermination may be evaluated based on information saved in entries 130of the printing devices that are stored in storage 710. After thedetermination of needed resources is made, step 906 executes by printingsystem 100 or managing sever 102 saving and refreshing the print joblist and order of the print jobs.

As described above with reference to FIG. 2 , the current status updatesof the printing devices may be sent to printing system 100 or managingserver 102 upon request or in subscription. Printing system 100 mayestablish a subscription 134 (see FIG. 2 ) on each printing device fordevice and print job statuses. Subscription 134 may provide updates andinformation to managing server 102. When a status change occurs for theprinting device or print jobs, the applicable printing device sends anotification 136 (in FIG. 2 ) to printing system 100.

Step 908 executes of printing system 100 or managing server 102receiving a notification of an applicable printing device. Thenotification may include, for example, referring to printing device 116,the status of paper cassette 1 may change from low paper to emptycassette. Printing device 116 sends notification 136 to this effect.Step 910 then executes by printing system 100 or managing server 102evaluating such a notification and saving the current information inentry 130 for information for printing device 116 on managing server102. Printing system 100 also may create historical data for printingdevice 116 that will be used for data analytics.

Step 912 executes of printing system 100 or managing server determiningif the notification received from an applicable printing device willcause an error or warning. If the answer is Yes, next step 914 executesof printing system 100 or managing server determining whether theerror/warning will cause or has caused the device to stop printing. Ifthe answer is Yes, step 916 may escalate this notification as a highestpriority error.

If the error/warning will not or has not caused the device to stopprinting, step 918 executes of printing system 100 or managing sever 102determining priority level of the error/warning. Different prioritylevels have been described above with reference to FIG. 2 .

Next, step 922 executes by displaying the error/warning on a displaypanel of the applicable printing device and step 924 executes bydisplaying suggestions on a display panel of the applicable printingdevice. Taking printing device 116 as an example, when the notificationindicates that the status of paper cassette 1 may change from low paperto empty cassette, the displayed suggestions may include loading morepapers on cassette 1.

Alternatively, step 920 executes by printing system 100 or managingserver 102 redirecting the print job to a different printing device.According to the preferred embodiments, printing system 100 or managingserver 102 may redirect a print job that will cause or has caused aprinting device to a different printing device when applicablesituations occur. Exemplary applicable situations may include those whenthe printing job is performed at night when users are not near theprinting device, when there are no suitable papers to be loaded in thepaper cassette, when there are no more toners, or when the printingdevice is out of order, and so on. The determination of the differentprinting device may be made based on current status updates saved inindividual entry 130 and data analytics information gathered from thecurrent status updates and historic data of each printing device. Theinformation of entry 130 have been described above with reference toFIG. 5 .

An alternative embodiment includes a method for resolving errors withina printing system is further disclosed. The method includes compilingerror information about errors from a plurality of printing devices,compiling pending job information for pending print jobs at theplurality of printing devices, analyzing the error information about theerrors from the plurality of printing devices, determining an errorcategory for each of the errors based on the error information, applyingweight parameters to each of the errors according to the respectiveerror category, analyzing the pending job information for the pendingprint jobs at the plurality of printing devices to determine resourcesspecified by each pending print job, indicating that the resourcesspecified by each pending print job will result in a potential error ata printing device of the plurality of printing devices, applying theweight parameters to the potential error, and determining a priorityorder to resolve the errors and the potential error based on the weightparameters and the pending job information for the pending print jobs.

A further alternative embodiment recites a method for resolving errorsat a printing device is also disclosed. The method includes compilingerror information about a plurality of errors, compiling pending jobinformation for pending print jobs at a print queue, analyzing the errorinformation about the plurality of errors, determining an error categoryfor each of the errors based on the error information, applying weightparameters to each of the errors according to the respective prioritycategory, analyzing the pending job information for the pending printjobs to determine resources specified by each pending print job,indicating that the resources specified by each pending print job willresult in a potential error within the printing device, applying theweight parameters to the potential error, and determining a priorityorder to resolve the errors and the potential error based on the weightparameters.

A yet alternative embodiment includes a print managing server for aprinting system is yet disclosed. The print management server includes aprocessor and a memory to store instructions executable on theprocessor. According to the embodiment, the instructions, when executed,configure the server to compile error information about errors from aplurality of printing devices, compile pending job information forpending print jobs at the plurality of printing devices, analyze theerror information about the errors from the plurality of printingdevices, determine an error category for each of the errors based on theerror information, apply weight parameters to each of the errorsaccording to the respective priority category, analyze the jobinformation for the pending print jobs at the plurality of printingdevices to determine resources for each pending print job, indicate thatthe resources for each pending print job will result in a potentialerror at the respective printing device, apply the weight parameters tothe potential error, and determine a priority order to resolve theerrors and the potential error based on the weight parameters and thejob information for the pending print jobs.

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer-usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,device, or propagation medium. More specific examples (a non-exhaustivelist) of the computer-readable medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a transmission media such as thosesupporting the Internet or an intranet, or a magnetic storage device.Note that the computer-usable or computer-readable medium could even bepaper or another suitable medium upon which the program is printed, asthe program can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork, including a local area network (LAN) or a wide area network(WAN), or the connection may be made to an external computer (forexample, through the Internet using an Internet Service Provider).

The present invention is described with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an” and “the” are intended toinclude plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specific thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

Embodiments may be implemented as a computer process, a computing systemor as an article of manufacture such as a computer program product ofcomputer readable media. The computer program product may be a computerstorage medium readable by a computer system and encoding a computerprogram instructions for executing a computer process. When accessed,the instructions cause a processor to enable other components to performthe functions disclosed above.

The corresponding structures, material, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material or act for performing the function incombination with other claimed elements are specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill without departingfrom the scope and spirit of the invention. The embodiment was chosenand described in order to best explain the principles of the inventionand the practical application, and to enable others of ordinary skill inthe art to understand the invention for embodiments with variousmodifications as are suited to the particular use contemplated.

One or more portions of the disclosed networks or systems may bedistributed across one or more MFP systems coupled to a network capableof exchanging information and data. Various functions and components ofthe MFP system may be distributed across multiple client computerplatforms, or configured to perform tasks as part of a distributedsystem. These components may be executable, intermediate or interpretedcode that communicates over the network using a protocol. The componentsmay have specified addresses or other designators to identify thecomponents within the network.

It will be apparent to those skilled in the art that variousmodifications to the disclosed may be made without departing from thespirit or scope of the invention. Thus, it is intended that the presentinvention covers the modifications and variations disclosed aboveprovided that these changes come within the scope of the claims andtheir equivalents.

What is claimed is:
 1. A method for resolving errors within a printingsystem, the method comprising: compiling error information about errorsfrom a plurality of printing devices; compiling pending job informationfor pending print jobs at the plurality of printing devices; analyzingthe error information about the errors from the plurality of printingdevices; determining an error category for each of the errors based onthe error information; applying weight parameters to each of the errorsaccording to the respective error category; analyzing the pending jobinformation for the pending print jobs at the plurality of printingdevices to determine resources specified by each pending print job;indicating that the resources specified by each pending print job willresult in a potential error at a printing device of the plurality ofprinting devices; applying the weight parameters to the potential error;and determining a priority order to resolve the errors and the potentialerror based on the weight parameters and the pending job information forthe pending print jobs.
 2. The method of claim 1, further comprisingparsing the pending print jobs at the plurality of printing devices todetermine the pending job information.
 3. The method of claim 2, whereinindicating includes determining a queued print job of the pending printjobs at the printing device will cause the potential error.
 4. Themethod of claim 1, wherein compiling the error information includescompiling warning information for the plurality of printing devices. 5.The method of claim 1, wherein the errors include at least oneprint-halting error having a first weight parameter, at least onepotential print-halting error having a second weight parameter, at leastone potential printing halting error based on at least one pending printjob having a third weight parameter, and at least one device errorhaving a fourth weight parameter.
 6. The method of claim 5, wherein thefirst weight parameter is greater than the second weight parameter, thethird weight parameter, and the fourth weight parameter.
 7. The methodof claim 1, further comprising compiling historical data for each of theplurality of printing devices.
 8. The method of claim 7, furthercomprising using the historical data to indicate that the resourcesspecified by the pending print jobs will cause the potential error. 9.The method of claim 1, further comprising updating the error informationor the pending job information upon receipt of a notification from theprinting device of the plurality of printing devices.
 10. A method forresolving errors at a printing device, the method comprising: compilingerror information about a plurality of errors; compiling pending jobinformation for pending print jobs at a print queue; analyzing the errorinformation about the plurality of errors; determining an error categoryfor each of the errors based on the error information; applying weightparameters to each of the errors according to the respective prioritycategory; analyzing the pending job information for the pending printjobs to determine resources specified by each pending print job;indicating that the resources specified by each pending print job willresult in a potential error within the printing device; applying theweight parameters to the potential error; and determining a priorityorder to resolve the errors and the potential error based on the weightparameters.
 11. The method of claim 1, further comprising displaying anotification on the printing device indicating a highest-priority errorin the priority order to resolve.
 12. The method of claim 1, wherein theerrors include at least one print-halting error having a first weightparameter, at least one potential print-halting error having a secondweight parameter, at least one potential printing halting error based onat least one pending print job having a third weight parameter, and atleast one device error having a fourth weight parameter.
 13. The methodof claim 12, further comprising ranking the at least one print-haltingerror having the first weight parameter above the at least one errorshaving the second weight parameter, the third weight parameter, or thefourth weight parameter.
 14. The method of claim 10, further comprisingcompiling historical data for the printing device.
 15. The method ofclaim 14, further comprising predicting the potential error within theprinting device using the historical data.
 16. A print managing serverfor a printing system, the print management server comprising: aprocessor; a memory to store instructions executable on the processor,the instructions, when executed, configure the server to compile errorinformation about errors from a plurality of printing devices; compilepending job information for pending print jobs at the plurality ofprinting devices; analyze the error information about the errors fromthe plurality of printing devices; determine an error category for eachof the errors based on the error information; apply weight parameters toeach of the errors according to the respective priority category;analyze the job information for the pending print jobs at the pluralityof printing devices to determine resources for each pending print job;indicate that the resources for each pending print job will result in apotential error at the respective printing device; apply the weightparameters to the potential error; and determine a priority order toresolve the errors and the potential error based on the weightparameters and the job information for the pending print jobs.
 17. Theprint management server of claim 16, wherein the instructions furtherconfigure the server to send a notification with the priority order. 18.The print management server of claim 16, wherein the instructionsfurther configure the server to compile data analytics for each of theplurality of printing devices.
 19. The print managing server of claim18, wherein the instructions further configure the server to use thedata analytics to indicate that the resources for the pending print jobswill cause the potential error.
 20. The print managing server of claim16, wherein the instructions further configure the server to parse thepending print jobs at the plurality of printing devices to determine thejob information.